ci: fix red badges — bump release to Node 22, drop duplicate release job#2
Merged
Merged
Conversation
The post-merge runs on main failed in the release stage: - release.yml ran semantic-release on Node 20.x, but semantic-release 25 requires Node ^22.14 || >=24.10 — it aborted before doing anything. Bump the release job to Node 22.x (CI test matrix was already updated). - ci.yml carried its own `release` job that ran semantic-release in parallel with release.yml. The duplicate raced on every push and its failure turned the CI badge red even though all tests passed. Remove it so ci.yml is test-only and release.yml is the single source of publishing (it also handles the JSR publish). Note: publishing still requires a valid NPM_TOKEN repo secret — the previous run failed token verification (EINVALIDNPMTOKEN), which must be refreshed in repo settings. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
|
🎉 This PR is included in version 1.6.0 🎉 The release is available on: Your semantic-release bot 📦🚀 |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Why
After merging #1, the CI and Release badges went red. Tests passed on every Node version (20/22/24) — the failures were entirely in the release stage:
release.ymlran on Node 20.x, but semantic-release 25 requires^22.14 || >=24.10. It aborted immediately:node version ^22.14.0 || >= 24.10.0 is required. Found v20.20.2. (The CI matrix was bumped in feat: modernize landing page, refresh favicon, fix TS6/Biome2.5 build #1, but this file was missed.)ci.ymlhad its ownreleasejob running semantic-release in parallel withrelease.yml. The duplicate raced on every push, and its failure turned the CI badge red even though all tests passed.What changed
release.yml: Node20.x→22.x.ci.yml: removed the redundantreleasejob. CI is now test-only;release.ymlis the single source of publishing (it also handles JSR).The release also failed npm token verification:
The
NPM_TOKENrepository secret is invalid/expired and must be refreshed:NPM_TOKEN.Until then the Release badge will stay red (the npm publish step can't authenticate). After this PR + a valid token, the next push to
mainshould publish cleanly and both badges go green.The CI badge will go green as soon as this merges (CI no longer runs a release step).